Parameter encoding techniques for wireless communication networks

ABSTRACT

Parameter encoding techniques for wireless communication networks are described. In some embodiments, an apparatus may comprise a memory and logic for a wireless communication device, at least a portion of the logic comprised in circuitry coupled to the memory, the logic to determine a channel usage configuration to be applied for a transmission of a packet to a remote device, the channel usage configuration to designate a primary channel and one or more data transmission channels, generate a PHY header for the packet, the PHY header to comprise a first field comprising information indicating the one or more data transmission channels and a second field comprising information identifying the primary channel, and encode the PHY header for wireless transmission. Other embodiments are described and claimed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, claims the benefit of andpriority to previously filed U.S. patent application Ser. No. 15/477,089filed Apr. 1, 2017, entitled “PARAMETER ENCODING TECHNIQUES FOR WIRELESSCOMMUNICATION NETWORKS”, which is hereby incorporated by reference inits entirety.

TECHNICAL FIELD

Embodiments described herein generally relate to wireless communicationsbetween devices in wireless networks.

BACKGROUND

In a given wireless communication network, a wireless communicationdevice may have the option of communicating via one of multiple possiblebandwidths and/or one or more of multiple possible portions of wirelessspectrum within a system bandwidth. Such a wireless communication devicemay also have the option of designating/utilizing one of multiplepossible channels as a primary channel. In order to enable successfulcommunication with other devices in the wireless network, the wirelesscommunication device may need to notify such other devices of thebandwidth and particular portions of wireless spectrum that it is using,as well as the primary channel that it is using.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a first operating environment.

FIG. 2 illustrates an embodiment of a first channelization scheme.

FIG. 3 illustrates an embodiment of a second channelization scheme.

FIG. 4 illustrates an embodiment of a second operating environment.

FIG. 5 illustrates an embodiment of a third operating environment.

FIG. 6 illustrates an embodiment of a fourth operating environment.

FIG. 7 illustrates an embodiment of a fifth operating environment.

FIG. 8 illustrates an embodiment of a first logic flow.

FIG. 9 illustrates an embodiment of a second logic flow.

FIG. 10A illustrates an embodiment of a first storage medium.

FIG. 10B illustrates an embodiment of a second storage medium.

FIG. 11 illustrates an embodiment of a device.

FIG. 12 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Various embodiments are generally directed to parameter encodingtechniques for wireless communication networks. In some embodiments, anapparatus may comprise a memory and logic for a wireless communicationdevice, at least a portion of the logic comprised in circuitry coupledto the memory, the logic to determine a channel usage configuration tobe applied for a transmission of a packet to a remote device, thechannel usage configuration to designate a primary channel and one ormore data transmission channels, generate a PHY header for the packet,the PHY header to comprise a first field comprising informationindicating the one or more data transmission channels and a second fieldcomprising information identifying the primary channel, and encode thePHY header for wireless transmission. Other embodiments are describedand claimed.

Various embodiments may comprise one or more elements. An element maycomprise any structure arranged to perform certain operations. Eachelement may be implemented as hardware, software, or any combinationthereof, as desired for a given set of design parameters or performanceconstraints. Although an embodiment may be described with a limitednumber of elements in a certain topology by way of example, theembodiment may include more or less elements in alternate topologies asdesired for a given implementation. It is worthy to note that anyreference to “one embodiment” or “an embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment. The appearances ofthe phrases “in one embodiment,” “in some embodiments,” and “in variousembodiments” in various places in the specification are not necessarilyall referring to the same embodiment.

Various embodiments herein are generally directed to wirelesscommunications systems. Some embodiments are particularly directed towireless communications over 60 GHz frequencies. Various suchembodiments may involve wireless communications performed according toone or more standards for 60 GHz wireless communications. For example,some embodiments may involve wireless communications performed accordingto one or more Wireless Gigabit Alliance (“WiGig”)/Institute ofElectrical and Electronics Engineers (IEEE) 802.11ad standards, such asthe IEEE 802.11ad-2012 standard published Dec. 28, 2012, including theirpredecessors, revisions, progeny, and/or variants. Various embodimentsmay involve wireless communications performed according to one or more“next-generation” 60 GHz (“NG60”) wireless local area network (WLAN)communications standards, such as the IEEE 802.11ay standard that iscurrently under development. Some embodiments may involve wirelesscommunications performed according to one or more millimeter-wave(mmWave) wireless communication standards. It is worthy of note that theterm “60 GHz,” as it is employed in reference to various wirelesscommunications devices, wireless communications frequencies, andwireless communications standards herein, is not intended tospecifically denote a frequency of exactly 60 GHz, but rather isintended to generally refer to frequencies in, or near, the 57 GHz to 64GHz frequency band or any nearby unlicensed band. The embodiments arenot limited in this context.

Various embodiments may additionally or alternatively involve wirelesscommunications according to one or more other wireless communicationstandards. Some embodiments may involve wireless communicationsperformed according to one or more broadband wireless communicationstandards. For example, various embodiments may involve wirelesscommunications performed according to one or more 3rd GenerationPartnership Project (3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPPLTE-Advanced (LTE-A) technologies and/or standards, including theirpredecessors, revisions, progeny, and/or variants. Additional examplesof broadband wireless communication technologies/standards that may beutilized in some embodiments may include—without limitation—GlobalSystem for Mobile Communications (GSM)/Enhanced Data Rates for GSMEvolution (EDGE), Universal Mobile Telecommunications System (UMTS)/HighSpeed Packet Access (HSPA), and/or GSM with General Packet Radio Service(GPRS) system (GSM/GPRS), IEEE 802.16 wireless broadband standards suchas IEEE 802.16m and/or IEEE 802.16p, International MobileTelecommunications Advanced (IMT-ADV), Worldwide Interoperability forMicrowave Access (WiMAX) and/or WiMAX II, Code Division Multiple Access(CDMA) 2000 (e.g., CDMA2000 1×RTT, CDMA2000 EV-DO, CDMA EV-DV, and soforth), High Performance Radio Metropolitan Area Network (HIPERMAN),Wireless Broadband (WiBro), High Speed Downlink Packet Access (HSDPA),High Speed Orthogonal Frequency-Division Multiplexing (OFDM) PacketAccess (HSOPA), High-Speed Uplink Packet Access (HSUPA) technologiesand/or standards, including their predecessors, revisions, progeny,and/or variants.

Further examples of wireless communications technologies and/orstandards that may be used in various embodiments may include—withoutlimitation—other IEEE wireless communication standards such as the IEEE802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE802.11u, IEEE 802.11ac, IEEE 802.11af, and/or IEEE 802.11ah standards,High-Efficiency Wi-Fi standards developed by the IEEE 802.11 HighEfficiency WLAN (HEW) Study Group and/or IEEE 802.11 Task Group (TG) ax,Wi-Fi Alliance (WFA) wireless communication standards such as Wi-Fi,Wi-Fi Direct, Wi-Fi Direct Services, WiGig Display Extension (WDE),WiGig Bus Extension (WBE), WiGig Serial Extension (WSE) standards and/orstandards developed by the WFA Neighbor Awareness Networking (NAN) TaskGroup, machine-type communications (MTC) standards such as thoseembodied in 3GPP Technical Report (TR) 23.887, 3GPP TechnicalSpecification (TS) 22.368, and/or 3GPP TS 23.682, and/or near-fieldcommunication (NFC) standards such as standards developed by the NFCForum, including any predecessors, revisions, progeny, and/or variantsof any of the above. The embodiments are not limited to these examples.

FIG. 1 illustrates an example of an operating environment 100 such asmay be representative of various embodiments. In operating environment100, a wireless communication device (WCD) 102 may wirelesslycommunicate in a wireless network 103. Wireless communication devices104-1, 104-2, 104-3, 104-4, 104-5, and 104-6 may also wirelesslycommunicate in wireless network 103 and/or with wireless communicationdevice 102. In various embodiments, wireless network 103 may comprise awireless network that utilizes wireless channel frequencies of the 60GHz band. In some embodiments, wireless communication devices withinwireless network 103 may communicate with each other according to one ormore standards for 60 GHz wireless communications. For example, invarious embodiments, devices within wireless network 103 may communicatewith each other according to one or more protocols and/or proceduresdefined in IEEE 802.11ad-2012, and/or its predecessors, revisions,progeny, and/or variants. In some embodiments, wireless communicationdevices 102, 104-1, 104-2, 104-3, 104-4, and 104-5 may comprise 60GHz-capable stations (STAs) such as Directional Multi-Gigabit (DMG)stations (STAs) or enhanced DMG (EDMG) STAs. In various embodiments,some or all of the wireless communication devices within wirelessnetwork 103 may communicate with each other according to one or moreprotocols and/or procedures that may be defined in the IEEE 802.11aystandard that is currently under development. In some embodiments,wireless communication device 102 may operate as a personal basicservice set (PBSS) control point/access point (PCP/AP). In variousembodiments, wireless communication devices 104-1, 104-2, 104-3, 104-4,and 104-5 may operate as non-PCP/AP STAs. The embodiments are notlimited in this context.

FIG. 2 illustrates an example of a channelization scheme 200 that may berepresentative of a channelization scheme that may be utilized by awireless communication protocol implemented in wireless network 103 ofFIG. 1 according to various embodiments. According to channelizationscheme 200, a plurality of wireless channels are defined, each of whichcorresponds to a different respective sub-band of a 60 GHz frequencyband 201. 60 GHz frequency band 201 spans from a lowest includedfrequency f_(L) to a highest included frequency f_(H), and thuscomprises a bandwidth BW that is equal to f_(H)−f_(L).

As reflected in FIG. 2, the channels defined by channelization scheme200 may include channels corresponding to sub-bands of various sizes. Inthis example, channelization scheme 200 defines non-overlapping 2.16 GHzchannels 1, 2, 3, 4, 5, and 6, each of which corresponds to a differentrespective 2.16 GHz sub-band. These 2.16 GHz channels may be referred toas the “base” channels of channelization scheme 200. Also shown arevarious “wide” channels, each of which corresponds to a respectivesub-band comprising the combined bandwidth of two or more base channels.In this example, the wide channels defined by channelization scheme 200include 4.32 GHz channels 9, 11, and 13, 6.48 GHz channels 17 and 20,and 8.64 GHz channel 25. Communication via any particular wide channelmay generally be implemented by bonding two or more contiguous basechannels and modulating across the combined bandwidth of those bondedchannels. In this context, the two or more 2.16 GHz base channels thatare bonded may be referred to as the “bonded channel set.” For example,with respect to 8.64 GHz channel 25, the bonded channel set may comprise2.16 GHz channels 1, 2, 3, and 4. The identities of the twelve channelsdepicted in FIG. 2, their sizes, and the bonded channel sets associatedwith the various wide channels are summarized in Table 1.

TABLE 1 Channel # Size Bonded Channel Set 1, 2, 3, 4, 5, 6 2.16 GHz — 94.32 GHz 1 and 2 11 4.32 GHz 3 and 4 13 4.32 GHz 5 and 6 17 6.48 GHz 1,2, and 3 20 6.48 GHz 4, 5, and 6 25 8.64 GHz 1, 2, 3, and 4

In various embodiments, channelization scheme 200 may be designed toconform to a rule that wide channels are not to overlap in the frequencydomain. In some other embodiments, channelization scheme 200 may permitoverlap between wide channels, and may define additional wide channelsnot depicted in FIG. 2. In an example embodiment in which overlapbetween wide channels is permitted, in addition to the twelve channelslisted in Table 1, channelization scheme 200 may define the six widechannels listed in Table 2, and thus a total of 18 channels. Theembodiments are not limited to this example.

TABLE 2 Channel # Size Bonded Channel Set 10 4.32 GHz 2 and 3 12 4.32GHz 4 and 5 18 6.48 GHz 2, 3, and 4 19 6.48 GHz 3, 4, and 5 26 8.64 GHz2, 3, 4, and 5 27 8.64 GHz 3, 4, 5, and 6

FIG. 3 illustrates an example of a channelization scheme 300 that may berepresentative of a channelization scheme that may be utilized by awireless communication protocol implemented in wireless network 103 ofFIG. 1 according to various embodiments. Like channelization scheme 200of FIG. 2, channelization scheme 300 defines a plurality of wirelesschannels, including channels corresponding to sub-bands of varioussizes. Each wireless channel defined by channelization scheme 300corresponds to a different respective sub-band of a 60 GHz frequencyband 301. 60 GHz frequency band 301 spans from a lowest includedfrequency f_(L)′ to a highest included frequency f_(H)′, and thuscomprises a bandwidth BW′ that is equal to f_(H)′-f_(L)′.

According to some embodiments, the bandwidth BW′ of 60 GHz frequencyband 301 may be larger than the bandwidth BW of 60 GHz frequency band201, which may enable the definition/inclusion of additional channelsrelative to channelization scheme 200 of FIG. 2. In various embodiments,the lowest included frequency f_(L)′ of 60 GHz frequency band 301 may belower than the lowest included frequency f_(L) of 60 GHz frequency band201 of FIG. 2. In some such embodiments, the highest included frequencyf_(H)′ of 60 GHz frequency band 301 may be equal to the highest includedfrequency f_(H) of 60 GHz frequency band 201 of FIG. 2. In otherembodiments in which f_(L′)<f_(L), f_(H)′ may differ from f_(H). Invarious embodiments, the highest included frequency f_(H)′ of 60 GHzfrequency band 301 may be greater than the highest included frequencyf_(H) of 60 GHz frequency band 201 of FIG. 2. In some such embodiments,f_(L′) may be equal to f_(L). In other embodiments in whichf_(H)′>f_(H), f_(L′) may differ from f_(L). The embodiments are notlimited in this context.

In the example depicted in FIG. 3, 60 GHz frequency band 301 is largeenough to accommodate eight non-overlapping 2.16 GHz basechannels—channels 1, 2, 3, 4, 5, 6, 7, and 8. Also defined are variouswide channels, including 4.32 GHz channels 9, 11, 13, and 15, 6.48 GHzchannels 17 and 21, and 8.64 GHz channels 25 and 29. The identities ofthe sixteen channels depicted in FIG. 3, their sizes, and the bondedchannel sets associated with the various wide channels are summarized inTable 3.

TABLE 3 Channel # Size Bonded Channel Set 1, 2, 3, 4, 5, 6, 7, 8 2.16GHz — 9 4.32 GHz 1 and 2 11 4.32 GHz 3 and 4 13 4.32 GHz 5 and 6 15 4.32GHz 7 and 8 17 6.48 GHz 1, 2, and 3 21 6.48 GHz 5, 6, and 7 25 8.64 GHz1, 2, 3, and 4 29 8.64 GHz 5, 6, 7, and 8

In various embodiments, channelization scheme 300 may be designed toconform to a rule that wide channels are not to overlap in the frequencydomain. In various other embodiments, channelization scheme 300 maypermit overlap between wide channels, and may define additional widechannels not depicted in FIG. 3. In an example embodiment in whichoverlap between wide channels is permitted, in addition to the sixteenchannels listed in Table 3, channelization scheme 300 may define the tenwide channels listed in Table 4, and thus a total of 26 channels. Theembodiments are not limited to this example.

TABLE 4 Channel # Size Bonded Channel Set 10 4.32 GHz 2 and 3 12 4.32GHz 4 and 5 14 4.32 GHz 6 and 7 18 6.48 GHz 2, 3, and 4 19 6.48 GHz 3,4, and 5 20 6.48 GHz 4, 5, and 6 22 6.48 GHz 6, 7, and 8 26 8.64 GHz 2,3, 4, and 5 27 8.64 GHz 3, 4, 5, and 6 28 8.64 GHz 4, 5, 6, and 7

FIG. 4 illustrates an example of an operating environment 400 such asmay be representative of various embodiments. In operating environment400, wireless communication device 102 may identify data that is to beprovided to wireless communication device 104-5. In order to providethat data to wireless communication device 104-5, wireless communicationdevice 102 may encapsulate it within a packet 406 and transmit thepacket 406 to wireless communication device 104-5. In variousembodiments, packet 406 may comprise a physical layer convergenceprotocol (PLCP) protocol data unit (PPDU). In some embodiments, packet406 may comprise a data field 410 that contains the data to be providedto wireless communication device 104-5.

In operating environment 400, devices in wireless network 103 maywirelessly communicate in accordance with a protocol that definesvarious different data transmission procedures, each of which maycorrespond to a different scheme for transmitting a packet viachannel(s) defined by a channelization scheme such as channelizationscheme 200 of FIG. 2 or channelization scheme 300 of FIG. 3. Accordingto any given one of such data transmission procedures, one or more 2.16GHz base channels may be used to convey a data field of a transmittedpacket, and may be referred to as the data transmission channel(s) withrespect to transmission of that packet. In various embodiments, the datatransmission procedures defined by the protocol may include a basechannel data transmission procedure, a wide channel data transmissionprocedure, and an aggregated carrier data transmission procedure.Transmission of a packet according to the base channel data transmissionprocedure may alternatively be referred to as transmission of thatpacket in “base channel mode.” Likewise, packet transmission accordingto the wide channel data transmission procedure may alternatively bereferred to as packet transmission in “wide channel mode,” and packettransmission according to the aggregated carrier data transmissionprocedure may alternatively be referred to as transmission of thatpacket in “aggregated carrier mode.”

In some embodiments, transmission of a packet in base channel mode mayinvolve transmitting a data field of that packet using a single datatransmission channel. For example, if wireless network 103 implementschannelization scheme 200 of FIG. 2 and wireless communication device102 transmits packet 406 in base channel mode, then it may transmit datafield 410 via a single data transmission channel comprising one of basechannels 1, 2, 3, 4, 5, and 6. The embodiments are not limited to thisexample.

In various embodiments, transmission of a packet in wide channel modemay involve transmitting a data field of that packet via a wide channelcorresponding to a bonded set of two or more 2.16 GHz base channels. Inthis context, the two or more 2.16 GHz base channels being bonded wouldconstitute the data transmission channels with respect to transmissionof the packet. For example, if wireless network 103 implementschannelization scheme 300 of FIG. 3, and wireless communication device102 transmits packet 406 in wide channel mode using 2.16 GHz basechannels 5, 6, 7, and 8 as data transmission channels, then it maytransmit data field 410 via 8.64 GHz channel 29. The embodiments are notlimited to this example.

In some embodiments, transmission of a packet in aggregated carrier modemay involve conveying a data field of that packet via an aggregated setof two or more 2.16 GHz base channels. In this context, the two or more2.16 GHz base channels being aggregated would constitute the datatransmission channels with respect to transmission of the packet. Unliketransmission in wide channel mode, which may involve performing a singlemodulation across the combined bandwidth of multiple data transmissionchannels (“the bonded channel set”), transmission in aggregated carriermode may involve separate parallel modulations of each of multiple datatransmission channels (“the aggregated channel set”). Transmission of apacket in aggregated carrier mode using two data transmission channelsmay also be referred to as transmission of that packet in “2.16 GHz+2.16GHz” mode. In an example of an embodiment involving transmission inaggregated carrier mode (and more particularly, 2.16 GHz+2.16 GHz mode),wireless network 103 may implement channelization scheme 300 of FIG. 3,and wireless communication device 102 may perform separate modulationsof 2.16 GHz base channels 5 and 7 in parallel in order to convey datafield 410. In the context of this example, 2.16 GHz base channels 5 and7 would constitute the data transmission channels with respect totransmission of packet 406. The embodiments are not limited to thisexample.

In various embodiments, in preparation for transmission of packet 406 towireless communication device 104-5, wireless communication device 102may be operative to determine a channel usage configuration that is tobe applied for transmission of packet 406. In some embodiments, theapplicable channel usage configuration for transmission of packet 406may designate an amount of bandwidth that is to be occupied inconjunction with transmission of packet 406. In the context of thattransmission, the designated amount of bandwidth may be referred to asthe “occupied bandwidth.” In various embodiments, the applicable channelusage configuration may specify a data transmission procedure accordingto which packet 406 is to be transmitted. In some embodiments, theapplicable channel usage configuration may designate one or more 2.16GHz base channels that are to serve as data transmission channels in thecontext of the transmission of packet 406 in the specified datatransmission mode.

In various embodiments, the applicable channel usage configuration mayalso designate a particular 2.16 GHz base channel as a primary channelin the context of the transmission of packet 406. In some embodiments,devices in wireless network 103 may communicate according to a protocolthat requires that the primary channel be a base channel thatcorresponds to a portion of wireless spectrum that is modulated inconjunction with transmission of data field 410—in other words, that theprimary channel also serve as a data transmission channel. A primarychannel of this type may be referred to as an “in-band” primary channel.In embodiments in which only in-band primary channels are permitted, theapplicable channel usage configuration may designate a particular datatransmission channel as the primary channel. In various otherembodiments, a protocol governing communications between devices inwireless network 103 may permit the primary channel to correspond to aportion of wireless spectrum that is not modulated in conjunction withtransmission of data field 410. A primary channel of this type may bereferred to as an “out-of-band” primary channel. In embodiments in whichboth in-band and out-of-band primary channels are permitted, the primarychannel designated by the applicable channel usage configuration may ormay not be a data transmission channel. The embodiments are not limitedin this context.

In operating environment 400, in order to successfully receive packet406 and obtain the data comprised in data field 410, wirelesscommunication device 104-5 may require knowledge of various aspects ofthe channel usage configuration, such as the applicable datatransmission mode, the identities of the primary channel and datatransmission channel(s), and the occupied bandwidth. In someembodiments, a wireless communication protocol implemented in wirelessnetwork 103 may define a notification mechanism via which devices inwireless network 103 may be informed of such parameters. In order tooptimize wireless communication performance within wireless network 103,it may be desirable that the notification mechanism be designed suchthat it makes this information available to devices in wireless network103 at a relatively low cost in terms of added overhead.

Disclosed herein are parameter encoding techniques that may beimplemented in various embodiments in order to enable devices such aswireless communication device 102 to notify other devices of channelusage configuration parameters in a manner involving relatively littleoverhead. According to some such techniques, a wireless communicationnetwork such as wireless communication network 103 may implement awireless communication protocol that defines a notification mechanismaccording to which a wireless communication device such as wirelesscommunication device 102 may use information elements such as indexvalues and/or bitmaps to specify channel usage configuration parametersassociated with its transmissions. In various embodiments, the wirelesscommunication device may include such information elements in PHYheaders of transmitted packets in order to notify receiving devices ofchannel usage configuration parameters associated with those packets.The embodiments are not limited in this context.

FIG. 5 illustrates an example of an operating environment 500 that maybe representative of the implementation of one or more of the disclosedparameter encoding techniques according to various embodiments. Inoperating environment 500, a wireless network 503 may implement aprotocol that defines a notification mechanism according to whichtransmitting devices inform other devices of channel usage configurationparameters associated with transmitted packets by includingconfiguration information within PHY headers of those packets. Using oneor more wireless communication channels of wireless network 503, awireless communication device 502 may wirelessly communicate with awireless communication device 504.

In various embodiments, wireless network 503 may comprise a wirelessnetwork that utilizes wireless channel frequencies of the 60 GHz band.In some embodiments, wireless communication devices 502 and 504 may beoperative to wirelessly communicate with each other according to one ormore standards for 60 GHz wireless communications. In variousembodiments, wireless communication devices 502 and 504 may be operativeto wirelessly communicate with each other according to one or moreprotocols and/or procedures defined in IEEE 802.11ad-2012, and/orpredecessors, revisions, progeny, and/or variants thereof. In someembodiments, wireless communication devices 502 and 504 may be operativeto wirelessly communicate with each other according to one or moreprotocols and/or procedures defined in one or more standards developedby IEEE 802.11 Task Group ay (TGay). In some embodiments, wirelesscommunication devices 502 and 504 may comprise 60 GHz-capable STAs, suchas DMG STAs or EDMG STAs. In various embodiments, wireless communicationdevice 502 may operate as a PCP/AP, and wireless communication device504 may operate as a non-PCP/AP STA. In various other embodiments,wireless communication device 504 may operate as a PCP/AP, and wirelesscommunication device 502 may operate as a non-PCP/AP STA. In yet otherembodiments, wireless communication devices 502 and 504 may both operateas non-PCP/AP STAs. The embodiments are not limited in this context.

In operating environment 500, having identified data to be provided towireless communication device 504, wireless communication device 502include that data in a data field 510 of a packet 506 that it transmitsto wireless communication device 504. Wireless communication device 502may notify wireless communication device 504 of various channel usageconfiguration parameters applicable to transmission of packet 506 byincluding configuration information 509 in a PHY header 508 of packet506. Based on configuration information 509, wireless communicationdevice 504 may identify the applicable channel usage configuration,enabling it to successfully receive packet 506 and obtain the datacontained in data field 510.

FIG. 6 illustrates an example of an operating environment 600 that maybe representative of the implementation of one or more of the disclosedparameter encoding techniques according to various embodiments. Moreparticularly, operating environment 600 may be representative of variousembodiments in which configuration information 509 of FIG. 5 is providedin the form of a single index value 614. In some embodiments, indexvalue 614 may uniquely identify a particular combination of channelusage configuration parameters. In various embodiments, for example,index value 614 may uniquely identify a particular combination ofoccupied bandwidth, data transmission mode (such as base channel mode,wide channel mode, or aggregated carrier mode), primary channel, anddata transmission channel(s). In some embodiments, index value 614 maybe comprised in a field 612, which may comprise a size (in bits)enabling the conveyance of each of a number of unique values that is atleast as large as a number of different permissible combinations ofchannel usage configuration parameters.

In various embodiments, devices in wireless network 503 may communicateaccording to a protocol that implements channelization scheme 200 ofFIG. 2 and permits out-of-band (OOB) primary channels. In suchembodiments, if overlap between wide channels is not permitted, theremay be a total of 104 possible combinations (listed in Table 5) ofoccupied bandwidth, data transmission channel(s), and primary channel.In order to accommodate this number of possible combinations, field 612may comprise a length of at least 7 bits. It is worthy of note that inembodiments in which overlap between wide channels is permitted, theremay be a greater number of possible combinations, potentiallynecessitating that field 612 comprise more than 7 bits. The embodimentsare not limited in this context.

TABLE 5 Occupied Pr. Ch. Data Tx No. of BW Type Mode Possible(DTC(s))_(PC) Combinations Comb'ns 2.16 GHz in-band BC (1)₁, (2)₂, (3)₃,(4)₄, (5)₅, (6)₆ 6 4.32 GHz in-band WC (1 · 2)₁, (1 · 2)₂, (3 · 4)₃, (3· 4)₄, (5 · 6)₅, (5 · 6)₆ 6 AC (1|2)₁, (1|2)₂, (1|3)₁, (1|3)₃, (1|4)₁,(1|4)₄, 30 (1|5)₁, (1|5)₅, (1|6)₁, (1|6)₆, (2|3)₂, (2|3)₃, (2|4)₂,(2|4)₄, (2|5)₂, (2|5)₅, (2|6)₂, (2|6)₆, (3|4)₃, (3|4)₄, (3|5)₃, (3|5)₅,(3|6)₃, (3|6)₆, (4|5)₄, (4|5)₅, (4|6)₄, (4|6)₆, (5|6)₅, (5|6)₆ OOB BC(1)₂, (2)₁, (3)₄, (4)₃, (5)₆, (6)₅ 6 6.48 GHz in-band WC (1 · 2 · 3)₁,(1 · 2 · 3)₂, (1 · 2 · 3)₃, (4 · 5 · 6)₄, (4 · 5 · 6)₅, 6 (4 · 5 · 6)₆OOB WC (1 · 2)₃, (2 · 3)₁, (4 · 5)₆, (5 · 6)₄ 4 AC (1|3)₂, (4|6)₅ 2 BC(1)₂, (1)₃, (2)₁, (2)₃, (3)₁, (3)₂, (4)₅, (4)₆, 12 (5)₄, (5)₆, (6)₄,(6)₅ 8.64 GHz in-band WC (1 · 2 · 3 · 4)₁, (1 · 2 · 3 · 4)₂, (1 · 2 · 3· 4)₃, (1 · 2 · 3 · 4)₄ 4 OOB WC (1 · 2 · 3)₄, (2 · 3 · 4)₁, (1 · 2)₃,(1 · 2)₄,(2 · 3)₁, 8 (2 · 3)₄, (3 · 4)₁, (3 · 4)₂ AC (1|2)₃, (1|2)₄,(1|3)₂, (1|3)₄, (1|4)₂, (1|4)₃, 12 (2|3)₁, (2|3)₄, (2|4)₁, (2|4)₃,(3|4)₁, (3|4)₂ BC (1)₃, (1)₄, (2)₃, (2)₄, (3)₁, (3)₂, (4)₁, (4)₂ 8 TOTALPOSSIBLE COMBINATIONS: 104

In some embodiments, devices in wireless network 503 may communicateaccording to a protocol that implements channelization scheme 300 ofFIG. 3 and permits out-of-band (OOB) primary channels. In suchembodiments, if overlap between wide channels is not permitted, theremay be a total of 168 possible combinations (listed in Table 6) ofoccupied bandwidth, data transmission channel(s), and primary channel.In order to accommodate this number of possible combinations, field 612may comprise a length of at least 8 bits. It is worthy of note that inembodiments in which overlap between wide channels is permitted, theremay be a greater number of possible combinations, potentiallynecessitating that field 612 comprise more than 8 bits. The embodimentsare not limited in this context.

TABLE 6 Occupied Pr. Ch. Data Tx No. of BW Type Mode Possible(DTC(s))_(PC) Combinations Comb'ns 2.16 GHz in-band BC (1)₁, (2)₂, (3)₃,(4)₄, (5)₅, (6)₆, (7)₇, (8)₈ 8 4.32 GHz in-band WC (1 · 2)₁, (1 · 2)₂,(3 · 4)₃, (3 · 4)₄, 8 (5 · 6)₅, (5 · 6)₆, (7 · 8)₇, (7 · 8)₈ AC (1|2)₁,(1|2)₂, (1|3)₁, (1|3)₃, (1|4)₁, (1|4)₄, 56 (1|5)₁, (1|5)₅, (1|6)₁,(1|6)₆, (1|7)₁, (1|7)₇, (1|8)₁, (1|8)₈, (2|3)₂, (2|3)₃, (2|4)₂, (2|4)₄,(2|5)₂, (2|5)₅, (2|6)₂, (2|6)₆, (2|7)₂, (2|7)₇, (2|8)₂, (2|8)₈, (3|4)₃,(3|4)₄, (3|5)₃, (3|5)₅, (3|6)₃, (3|6)₆, (3|7)₃, (3|7)₇, (3|8)₃, (3|8)₈,(4|5)₄, (4|5)₅, (4|6)₄, (4|6)₆, (4|7)₄, (4|7)₇, (4|8)₄, (4|8)₈, (5|6)₅,(5|6)₆, (5|7)₅, (5|7)₇, (5|8)₅, (5|8)₈, (6|7)₆, (6|7)₇, (6|8)₆, (6|8)₈,(7|8)₇, (7|8)₈ OOB BC (1)₂, (2)₁, (3)₄, (4)₃, (5)₆, (6)₅, (7)₈, (8)₇ 86.48 GHz in-band WC (1 · 2 · 3)₁, (1 · 2 · 3)₂, (1 · 2 · 3)₃, (5 · 6 ·7)₅, 6 (5 · 6 · 7)₆, (5 · 6 · 7)₇ OOB WC (1 · 2)₃, (2 · 3)₁, (5 · 6)₇,(6 · 7)₅ 4 AC (1|3)₂, (5|7)₆ 2 BC (1)₂, (1)₃, (2)₁, (2)₃, (3)₁, (3)₂,(5)₆, 12 (5)₇, (6)₅, (6)₇, (7)₅, (7)₆ 8.64 GHz in-band WC (1 · 2 · 3 ·4)₁, (1 · 2 · 3 · 4)₂, (1 · 2 · 3 · 4)₃, (1 · 2 · 3 · 4)₄, 8 (5 · 6 · 7· 8)₅, (5 · 6 · 7 · 8)₆, (5 · 6 · 7 · 8)₇, (5 · 6 · 7 · 8)₈ OOB WC (1 ·2 · 3)₄, (2 · 3 · 4)₁, (1 · 2)₃, (1 · 2)₄, (2 · 3)₁, 16 (2 · 3)₄, (3 ·4)₁, (3 · 4)₂, (5 · 6 · 7)₈, (6 · 7 · 8)₅, (5 · 6)₇, (5 · 6)₈, (6 · 7)₅,(6 · 7)₈, (7 · 8)₅, (7 · 8)₆ AC (1|2)₃, (1|2)₄, (1|3)₂, (1|3)₄, (1|4)₂,(1|4)₃, 24 (2|3)₁, (2|3)₄, (2|4)₁, (2|4)₃, (3|4)₁, (3|4)₂, (5|6)₇,(5|6)₈, (5|7)₆, (5|7)₈, (5|8)₆, (5|8)₇, (6|7)₅, (6|7)₈, (6|8)₅, (6|8)₇,(7|8)₅, (7|8)₆ BC (1)₃, (1)₄, (2)₃, (2)₄, (3)₁, (3)₂, (4)₁, (4)₂, 16(5)₇, (5)₈, (6)₇, (6)₈, (7)₅, (7)₆, (8)₅, (8)₆ TOTAL POSSIBLECOMBINATIONS: 168

In some embodiments, wireless communication device 502 may generally beoperative to identify index value 614 based on a mapping schemeaccording to which respective index values are mapped to variouspossible channel usage configurations. In some embodiments, in order toenable application of such a mapping scheme, wireless communicationdevice 502 may be operative to determine a primary channel identifier(ID) 616 and one or more data transmission channel ID(s) 618. Primarychannel ID 616 may comprise a channel ID associated with the primarychannel designated by the applicable channel usage configuration. Datatransmission channel ID(s) 618 may comprise one or more channel IDs,each one of which may comprise a channel ID associated with a respectiveone of the one or more data transmission channels designated by theapplicable channel usage configuration.

In various embodiments, wireless communication device 502 may apply amapping scheme to identify index value 614 based on primary channel ID616 and transmission channel ID(s) 618. In some such embodiments,wireless communication device 502 may determine an offset value 620based on the occupied bandwidth and the data transmission mode, and mayidentify index value 614 based on primary channel ID 616, transmissionchannel ID(s) 618, and offset value 620. The embodiments are not limitedin this context.

In various embodiments, wireless communication device 504 may identifythe index value 614 comprised in field 612, and may then identify achannel usage configuration that corresponds to that index value 614. Insome embodiments, wireless communication device 504 may then apply theidentified channel usage configuration for reception of data field 510.In various embodiments, based on index value 614, wireless communicationdevice 504 may determine primary channel ID 616 and data transmissionchannel ID(s) 618. In some embodiments, based on index value 614,wireless communication device 504 may identify an occupied bandwidthand/or a data transmission mode associated with transmission of packet506. The embodiments are not limited in this context.

FIG. 7 illustrates an example of an operating environment 700 that maybe representative of the implementation of one or more of the disclosedparameter encoding techniques according to various embodiments. Moreparticularly, operating environment 700 may be representative of variousembodiments in which two fields are used to provide wirelesscommunication device 504 with configuration information for use inidentifying the applicable channel usage configuration for packet 506.In operating environment 700, wireless communication device 502 mayinclude configuration information 709A in a field 712A of PHY header508, and may include configuration information 709B in a field 712B ofPHY header 508. In some embodiments, configuration information 709A maycomprise information identifying the data transmission channel(s) withrespect to transmission of packet 506, and configuration information709B may comprise information identifying the primary channel for thattransmission. In various embodiments, configuration information 709B maycomprise a three-bit value indicating a 2.16 GHz base channel thatcomprises the primary channel. The embodiments are not limited in thiscontext.

In some embodiments, configuration information 709A may take the form ofan index value of a similar nature as index value 614. In various suchembodiments, the use of separate field 712B to convey configurationinformation 709B indicating the identity of the primary channel mayreduce the number of different possible index values that need to beaccommodated by field 712A (relative to field 612 in operatingenvironment 600 of FIG. 6). For example, if devices in wireless network503 communicate according to a protocol that implements channelizationscheme 200 of FIG. 2 and wide channel overlap is not permitted, thenfield 712A may only need to accommodate 27 different possible indexvalues instead of 104, and may thus be implemented using only 5 bitsinstead of 7. Similarly, if devices in wireless network 503 communicateaccording to a protocol that implements channelization scheme 300 ofFIG. 3 and wide channel overlap is not permitted, then field 712B mayonly need to accommodate 44 different possible index values instead of168, and may thus be implemented using only 6 bits instead of 8. Theembodiments are not limited to these examples.

In some embodiments, rather than comprising an index value, theconfiguration information 709A in field 712A may comprise a bitmap. Invarious embodiments, each bit of the bitmap may be set to indicatewhether a respective 2.16 GHz base channel constitutes a datatransmission channel with respect to transmission of packet 506. In someembodiments, field 712A may contain a 6-bit bitmap, each bit of whichmay correspond to a respective one of 2.16 GHz base channels 1-6 ofchannelization scheme 200 of FIG. 2. In various embodiments, field 712Amay contain an 8-bit bitmap, each bit of which may correspond to arespective one of 2.16 GHz base channels 1-8 of channelization scheme300 of FIG. 3. In some embodiments, PHY header 508 may include a bit setto indicate whether packet 506 is being transmitted in aggregatedcarrier mode. In various embodiments, in the event that a bitmap infield 712A indicates the use of multiple contiguous 2.16 GHz basechannels, the inclusion of such a bit may enable wireless communicationdevice 504 to determine whether those contiguous channels are beingbonded or aggregated in conjunction with transmission of packet 506. Theembodiments are not limited in this context.

Operations for the above embodiments may be further described withreference to the following figures and accompanying examples. Some ofthe figures may include a logic flow. Although such figures presentedherein may include a particular logic flow, it can be appreciated thatthe logic flow merely provides an example of how the generalfunctionality as described herein can be implemented. Further, the givenlogic flow does not necessarily have to be executed in the orderpresented unless otherwise indicated. In addition, the given logic flowmay be implemented by a hardware element, a software element executed bya processor, or any combination thereof. The embodiments are not limitedin this context.

FIG. 8 illustrates an example of a logic flow 800 that may berepresentative of operations that may be performed according to one ormore of the disclosed parameter encoding techniques in variousembodiments. For example, logic flow 800 may be representative ofoperations that may be performed by wireless communication device 502 inoperating environment 500 of FIG. 5 according to some embodiments. Asshown in FIG. 8, a channel usage configuration that is to be applied fortransmission of a packet to a remote device may be determined at 802.For example, in operating environment 700 of FIG. 7, wirelesscommunication device 502 may determine a channel usage configurationthat is to be applied for transmission of packet 506 to wirelesscommunication device 504. At 804, a PHY header of the packet may begenerated, and the PHY header may comprise a first field indicating oneor more data transmission channels and a second field indicating aprimary channel. For example, in operating environment 700 of FIG. 7,wireless communication device 502 may generate PHY header 508, which maycomprise a field 712A containing configuration information 709Aindicating one or more data transmission channels, and a field 712Bcontaining configuration information 709B indicating a primary channel.At 806, the PHY header may be encoded for wireless transmission. Forexample, in operating environment 700 of FIG. 7, wireless communicationdevice 502 may encode PHY header 508 for wireless transmission towireless communication device 504. The embodiments are not limited tothese examples.

FIG. 9 illustrates an example of a logic flow 900 that may berepresentative of operations that may be performed according to one ormore of the disclosed parameter encoding techniques in variousembodiments. For example, logic flow 900 may be representative ofoperations that may be performed by wireless communication device 504 inoperating environment 700 of FIG. 7 according to some embodiments. Asshown in FIG. 9, a PHY header for a packet to be received from a remotedevice may be decoded at 902. For example, in operating environment 700of FIG. 7, wireless communication device 504 may decode the PHY header508 of packet 506. At 904, a primary channel may be identified based ona field comprised in the PHY header. For example, in operatingenvironment 700 of FIG. 7, wireless communication device 504 mayidentify the primary channel based on configuration information 709Bcomprised in field 712B of PHY header 508. At 906, one or more datatransmission channels may be identified based on a field comprised inthe PHY header. For example, in operating environment 700 of FIG. 7,wireless communication device 504 may identify one or more datatransmission channels based on configuration information 709A comprisedin field 712A of PHY header 508. At 908, a data field of the packet maybe received via the one or more data transmission channels. For example,in operating environment 700 of FIG. 7, wireless communication device504 may receive data field 510 via one or more data transmissionchannels identified based on configuration information 709A comprised infield 712A of PHY header 508. The embodiments are not limited to theseexamples.

Various embodiments of the invention may be implemented fully orpartially in software and/or firmware. This software and/or firmware maytake the form of instructions contained in or on a computer-readablestorage medium, which may comprise a non-transitory storage mediumaccording to some embodiments. Those instructions may then be read andexecuted by one or more processors to enable performance of theoperations described herein. The instructions may be in any suitableform, such as but not limited to source code, compiled code, interpretedcode, executable code, static code, dynamic code, and the like. Such acomputer-readable medium may generally comprise any medium suitable forstoring information in a form readable by one or more computers, such asbut not limited to read only memory (ROM); random access memory (RAM);magnetic disk storage media; optical storage media; a flash memory, etc.The embodiments are not limited in this context.

FIG. 10A illustrates an embodiment of a storage medium 1000. Storagemedium 1000 may comprise any computer-readable storage medium ormachine-readable storage medium, such as an optical, magnetic orsemiconductor storage medium. In various embodiments, storage medium1000 may comprise an article of manufacture. In some embodiments,storage medium 1000 may comprise a non-transitory storage medium. Insome embodiments, storage medium 1000 may store computer-executableinstructions 1002 that generally comprise instructions for implementingone or more of the disclosed parameter encoding techniques. In variousembodiments, computer-executable instructions 1002 may includeinstructions for implementing one or both of wireless communicationdevice 102 and wireless communication device 502. In some embodiments,computer-executable instructions 1002 may include instructions forimplementing any of wireless communication devices 104-1 to 104-6 and/orwireless communication device 504. Examples of a computer-readablestorage medium or machine-readable storage medium may include anytangible media capable of storing electronic data, including volatilememory or non-volatile memory, removable or non-removable memory,erasable or non-erasable memory, writeable or re-writeable memory, andso forth. Examples of computer-executable instructions may include anysuitable type of code, such as source code, compiled code, interpretedcode, executable code, static code, dynamic code, object-oriented code,visual code, and the like. The embodiments are not limited in thiscontext.

FIG. 10B illustrates an embodiment of a storage medium 1050. Storagemedium 1050 may comprise any computer-readable storage medium ormachine-readable storage medium, such as an optical, magnetic orsemiconductor storage medium. In various embodiments, storage medium1050 may comprise an article of manufacture. In some embodiments,storage medium 1050 may comprise a non-transitory storage medium. Insome embodiments, storage medium 1000 may store computer-executableinstructions, such as computer-executable instructions to implement oneor both of logic flows 800 and 900. Examples of a computer-readablestorage medium or machine-readable storage medium and ofcomputer-executable instructions may include any of the respectiveexamples discussed above in reference to storage medium 1000 of FIG.10A. The embodiments are not limited in this context.

FIG. 11 illustrates an embodiment of a communications device 1100 thatmay implement one or more of wireless communication device 102, wirelesscommunication devices 104-1 to 104-6, wireless communication device 502,wireless communication device 504, logic flow 800, logic flow 900,storage medium 1000, and storage medium 1050 according to variousembodiments. In various embodiments, device 1100 may comprise a logiccircuit 1128. The logic circuit 1128 may include physical circuits toperform operations described for one or more of wireless communicationdevice 102, wireless communication devices 104-1 to 104-6, wirelesscommunication device 502, wireless communication device 504, logic flow800, and logic flow 900, for example. As shown in FIG. 11, device 1100may include a radio interface 1110, baseband circuitry 1120, andcomputing platform 1130, although the embodiments are not limited tothis configuration.

The device 1100 may implement some or all of the structure and/oroperations for one or more of wireless communication device 102,wireless communication devices 104-1 to 104-6, wireless communicationdevice 502, wireless communication device 504, logic flow 800, logicflow 900, storage medium 1000, storage medium 1050, and logic circuit1128 in a single computing entity, such as entirely within a singledevice. Alternatively, the device 1100 may distribute portions of thestructure and/or operations for one or more of wireless communicationdevice 102, wireless communication devices 104-1 to 104-6, wirelesscommunication device 502, wireless communication device 504, logic flow800, logic flow 900, storage medium 1000, storage medium 1050, and logiccircuit 1128 across multiple computing entities using a distributedsystem architecture, such as a client-server architecture, a 3-tierarchitecture, an N-tier architecture, a tightly-coupled or clusteredarchitecture, a peer-to-peer architecture, a master-slave architecture,a shared database architecture, and other types of distributed systems.The embodiments are not limited in this context.

In one embodiment, radio interface 1110 may include a component orcombination of components adapted for transmitting and/or receivingsingle-carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK), orthogonal frequency divisionmultiplexing (OFDM), and/or single-carrier frequency division multipleaccess (SC-FDMA) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. Radiointerface 1110 may include, for example, a receiver 1112, a frequencysynthesizer 1114, and/or a transmitter 1116. Radio interface 1110 mayinclude bias controls, a crystal oscillator and/or one or more antennas1118-f In another embodiment, radio interface 1110 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 1120 may communicate with radio interface 1110 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 1122 for down converting received signals, adigital-to-analog converter 1124 for up converting signals fortransmission. Further, baseband circuitry 1120 may include a baseband orphysical layer (PHY) processing circuit 1126 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry1120 may include, for example, a medium access control (MAC) processingcircuit 1127 for MAC/data link layer processing. Baseband circuitry 1120may include a memory controller 1132 for communicating with MACprocessing circuit 1127 and/or a computing platform 1130, for example,via one or more interfaces 1134.

In some embodiments, PHY processing circuit 1126 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames. Alternatively or in addition, MAC processingcircuit 1127 may share processing for certain of these functions orperform these processes independent of PHY processing circuit 1126. Insome embodiments, MAC and PHY processing may be integrated into a singlecircuit.

The computing platform 1130 may provide computing functionality for thedevice 1100. As shown, the computing platform 1130 may include aprocessing component 1140. In addition to, or alternatively of, thebaseband circuitry 1120, the device 1100 may execute processingoperations or logic for one or more of wireless communication device102, wireless communication devices 104-1 to 104-6, wirelesscommunication device 502, wireless communication device 504, logic flow800, logic flow 900, storage medium 1000, storage medium 1050, and logiccircuit 1128 using the processing component 1140. The processingcomponent 1140 (and/or PHY 1126 and/or MAC 1127) may comprise varioushardware elements, software elements, or a combination of both. Examplesof hardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

The computing platform 1130 may further include other platformcomponents 1150. Other platform components 1150 include common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components (e.g., digital displays), powersupplies, and so forth. Examples of memory units may include withoutlimitation various types of computer readable and machine readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Device 1100 may be, for example, an ultra-mobile device, a mobiledevice, a fixed device, a machine-to-machine (M2M) device, a personaldigital assistant (PDA), a mobile computing device, a smart phone, atelephone, a digital telephone, a cellular telephone, user equipment,eBook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, display, television,digital television, set top box, wireless access point, base station,node B, subscriber station, mobile subscriber center, radio networkcontroller, router, hub, gateway, bridge, switch, machine, orcombination thereof. Accordingly, functions and/or specificconfigurations of device 1100 described herein, may be included oromitted in various embodiments of device 1100, as suitably desired.

Embodiments of device 1100 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1118-f) for transmissionand/or reception using adaptive antenna techniques for beamforming orspatial division multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of device 1100 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 1100 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 1100 shown in theblock diagram of FIG. 11 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

FIG. 12 illustrates an embodiment of a wireless network 1200. As shownin FIG. 12, wireless network comprises an access point 1202 and wirelessstations 1204, 1206, and 1208. In various embodiments, wireless network1200 may comprise a wireless local area network (WLAN), such as a WLANimplementing one or more Institute of Electrical and ElectronicsEngineers (IEEE) 802.11/15 standards (sometimes collectively referred toas “Wi-Fi”). In some other embodiments, wireless network 1200 maycomprise another type of wireless network, and/or may implement otherwireless communications standards. In various embodiments, for example,wireless network 1200 may comprise a WWAN or WPAN rather than a WLAN.The embodiments are not limited to this example.

In some embodiments, wireless network 1200 may implement one or morebroadband wireless communications standards, such as 3G or 4G standards,including their revisions, progeny, and variants. Examples of 3G or 4Gwireless standards may include without limitation any of the IEEE802.16m and 802.16p standards, 3rd Generation Partnership Project (3GPP)Long Term Evolution (LTE) and LTE-Advanced (LTE-A) standards, andInternational Mobile Telecommunications Advanced (IMT-ADV) standards,including their revisions, progeny and variants. Other suitable examplesmay include, without limitation, Global System for Mobile Communications(GSM)/Enhanced Data Rates for GSM Evolution (EDGE) technologies,Universal Mobile Telecommunications System (UMTS)/High Speed PacketAccess (HSPA) technologies, Worldwide Interoperability for MicrowaveAccess (WiMAX) or the WiMAX II technologies, Code Division MultipleAccess (CDMA) 2000 system technologies (e.g., CDMA2000 1×RTT, CDMA2000EV-DO, CDMA EV-DV, and so forth), High Performance Radio MetropolitanArea Network (HIPERMAN) technologies as defined by the EuropeanTelecommunications Standards Institute (ETSI) Broadband Radio AccessNetworks (BRAN), Wireless Broadband (WiBro) technologies, GSM withGeneral Packet Radio Service (GPRS) system (GSM/GPRS) technologies, HighSpeed Downlink Packet Access (HSDPA) technologies, High Speed OrthogonalFrequency-Division Multiplexing (OFDM) Packet Access (HSOPA)technologies, High-Speed Uplink Packet Access (HSUPA) systemtechnologies, 3GPP Rel. 8-12 of LTE/System Architecture Evolution (SAE),and so forth. The embodiments are not limited in this context.

In various embodiments, wireless stations 1204, 1206, and 1208 maycommunicate with access point 1202 in order to obtain connectivity toone or more external data networks. In some embodiments, for example,wireless stations 1204, 1206, and 1208 may connect to the Internet 1212via access point 1202 and access network 1210. In various embodiments,access network 1210 may comprise a private network that providessubscription-based Internet-connectivity, such as an Internet ServiceProvider (ISP) network. The embodiments are not limited to this example.

In various embodiments, two or more of wireless stations 1204, 1206, and1208 may communicate with each other directly by exchanging peer-to-peercommunications. For example, in the example of FIG. 12, wirelessstations 1204 and 1206 communicate with each other directly byexchanging peer-to-peer communications 1214. In some embodiments, suchpeer-to-peer communications may be performed according to one or moreWi-Fi Alliance (WFA) standards. For example, in various embodiments,such peer-to-peer communications may be performed according to the WFAWi-Fi Direct standard, 2010 Release. In various embodiments, suchpeer-to-peer communications may additionally or alternatively beperformed using one or more interfaces, protocols, and/or standardsdeveloped by the WFA Wi-Fi Direct Services (WFDS) Task Group. Theembodiments are not limited to these examples.

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor. Some embodiments maybe implemented, for example, using a machine-readable medium or articlewhich may store an instruction or a set of instructions that, ifexecuted by a machine, may cause the machine to perform a method and/oroperations in accordance with the embodiments. Such a machine mayinclude, for example, any suitable processing platform, computingplatform, computing device, processing device, computing system,processing system, computer, processor, or the like, and may beimplemented using any suitable combination of hardware and/or software.The machine-readable medium or article may include, for example, anysuitable type of memory unit, memory device, memory article, memorymedium, storage device, storage article, storage medium and/or storageunit, for example, memory, removable or non-removable media, erasable ornon-erasable media, writeable or re-writeable media, digital or analogmedia, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM),Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW),optical disk, magnetic media, magneto-optical media, removable memorycards or disks, various types of Digital Versatile Disk (DVD), a tape, acassette, or the like. The instructions may include any suitable type ofcode, such as source code, compiled code, interpreted code, executablecode, static code, dynamic code, encrypted code, and the like,implemented using any suitable high-level, low-level, object-oriented,visual, compiled and/or interpreted programming language.

The following examples pertain to further embodiments:

Example 1 is an apparatus, comprising a memory, and logic for a wirelesscommunication device, at least a portion of the logic comprised incircuitry coupled to the memory, the logic to determine a channel usageconfiguration to be applied for a transmission of a packet to a remotedevice, the channel usage configuration to designate a primary channeland one or more transmission channels, generate a PHY header for thepacket, the PHY header to comprise a first field comprising informationindicating the one or more transmission channels, and a second fieldcomprising information identifying the primary channel, and encode thePHY header for wireless transmission.

Example 2 is the apparatus of Example 1, the channel usage configurationto designate a single transmission channel.

Example 3 is the apparatus of Example 2, the single transmission channelto comprise a 2.16 GHz channel.

Example 4 is the apparatus of Example 3, the primary channel to comprisea same 2.16 GHz channel as the single transmission channel.

Example 5 is the apparatus of Example 3, the primary channel to comprisea second 2.16 GHz channel.

Example 6 is the apparatus of Example 2, the single transmission channelto comprise a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64 GHzchannel.

Example 7 is the apparatus of Example 6, the primary channel to comprisean in-band 2.16 GHz channel that overlaps the single transmissionchannel.

Example 8 is the apparatus of Example 6, the primary channel to comprisean out-of-band 2.16 GHz channel that does not overlap the singletransmission channel.

Example 9 is the apparatus of Example 1, the channel usage configurationto designate multiple transmission channels.

Example 10 is the apparatus of Example 9, the channel usageconfiguration to designate two 2.16 GHz transmission channels.

Example 11 is the apparatus of Example 10, the primary channel tocomprise a same 2.16 GHz channel as one of the two 2.16 GHz transmissionchannels.

Example 12 is the apparatus of Example 10, the primary channel tocomprise a third 2.16 GHz channel.

Example 13 is the apparatus of any of Examples 1 to 12, the first fieldto comprise an index value indicating the one or more transmissionchannels.

Example 14 is the apparatus of any of Examples 1 to 12, the first fieldto comprise a bitmap indicating the one or more transmission channels.

Example 15 is the apparatus of Example 14, the bitmap to comprise 8bits.

Example 16 is the apparatus of Example 15, each of the 8 bits tocorrespond to a respective 2.16 GHz channel.

Example 17 is the apparatus of any of Examples 1 to 16, the second fieldto comprise a three-bit value.

Example 18 is the apparatus of Example 17, the three-bit value toindicate which one of eight 2.16 GHz channels constitutes the primarychannel.

Example 19 is the apparatus of any of Examples 1 to 18, the PHY headerto comprise a bit indicating whether channel aggregation is to be usedfor transmission of the packet.

Example 20 is the apparatus of Example 19, the logic to set the bit toindicate that channel aggregation is to be used when the channel usageconfiguration designates more than one transmission channel.

Example 21 is a system, comprising an apparatus according to any ofExamples 1 to 20, and at least one radio frequency (RF) transceiver.

Example 22 is the system of Example 21, comprising at least oneprocessor.

Example 23 is the system of any of Examples 21 to 22, comprising atleast one RF antenna.

Example 24 is an apparatus, comprising a memory, and logic for awireless communication device, at least a portion of the logic comprisedin circuitry coupled to the memory, the logic to decode a PHY header fora packet to be received from a remote device, the PHY header to indicatea channel usage configuration to be applied for reception of the packet,identify, based on a first field comprised in the PHY header, a primarychannel designated by the channel usage configuration, identify, basedon a second field comprised in the PHY header, one or more transmissionchannels designated by the channel usage configuration, and receive adata field of the packet via the one or more transmission channels.

Example 25 is the apparatus of Example 24, the channel usageconfiguration to designate a single transmission channel.

Example 26 is the apparatus of Example 25, the single transmissionchannel to comprise a 2.16 GHz channel.

Example 27 is the apparatus of Example 26, the primary channel tocomprise a same 2.16 GHz channel as the single transmission channel.

Example 28 is the apparatus of Example 26, the primary channel tocomprise a second 2.16 GHz channel.

Example 29 is the apparatus of Example 25, the single transmissionchannel to comprise a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64GHz channel.

Example 30 is the apparatus of Example 29, the primary channel tocomprise an in-band 2.16 GHz channel that overlaps the singletransmission channel.

Example 31 is the apparatus of Example 29, the primary channel tocomprise an out-of-band 2.16 GHz channel that does not overlap thesingle transmission channel.

Example 32 is the apparatus of Example 24, the channel usageconfiguration to designate multiple transmission channels.

Example 33 is the apparatus of Example 32, the channel usageconfiguration to designate two 2.16 GHz transmission channels.

Example 34 is the apparatus of Example 33, the primary channel tocomprise a same 2.16 GHz channel as one of the two 2.16 GHz transmissionchannels.

Example 35 is the apparatus of Example 33, the primary channel tocomprise a third 2.16 GHz channel.

Example 36 is the apparatus of any of Examples 24 to 35, the secondfield to comprise an index value indicating the one or more transmissionchannels.

Example 37 is the apparatus of any of Examples 24 to 35, the secondfield to comprise a bitmap indicating the one or more transmissionchannels.

Example 38 is the apparatus of Example 37, the bitmap to comprise 8bits.

Example 39 is the apparatus of Example 38, each of the 8 bits tocorrespond to a respective 2.16 GHz channel.

Example 40 is the apparatus of any of Examples 24 to 39, the first fieldto comprise a three-bit value.

Example 41 is the apparatus of Example 40, the three-bit value toindicate which one of eight 2.16 GHz channels constitutes the primarychannel.

Example 42 is the apparatus of any of Examples 24 to 41, the PHY headerto comprise a bit indicating whether channel aggregation is to be usedfor transmission of the packet.

Example 43 is a system, comprising an apparatus according to any ofExamples 24 to 42, and at least one radio frequency (RF) transceiver.

Example 44 is the system of Example 43, comprising at least oneprocessor.

Example 45 is the system of any of Examples 43 to 44, comprising atleast one RF antenna.

Example 46 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted at a wireless communication device, cause the wirelesscommunication device to determine a channel usage configuration to beapplied for a transmission of a packet to a remote device, the channelusage configuration to designate a primary channel and one or moretransmission channels, generate a PHY header for the packet, the PHYheader to comprise a first field comprising information indicating theone or more transmission channels, and a second field comprisinginformation identifying the primary channel, and encode the PHY headerfor wireless transmission.

Example 47 is the at least one non-transitory computer-readable storagemedium of Example 46, the channel usage configuration to designate asingle transmission channel.

Example 48 is the at least one non-transitory computer-readable storagemedium of Example 47, the single transmission channel to comprise a 2.16GHz channel.

Example 49 is the at least one non-transitory computer-readable storagemedium of Example 48, the primary channel to comprise a same 2.16 GHzchannel as the single transmission channel.

Example 50 is the at least one non-transitory computer-readable storagemedium of Example 48, the primary channel to comprise a second 2.16 GHzchannel.

Example 51 is the at least one non-transitory computer-readable storagemedium of Example 47, the single transmission channel to comprise a 4.32GHz channel, a 6.48 GHz channel, or an 8.64 GHz channel.

Example 52 is the at least one non-transitory computer-readable storagemedium of Example 51, the primary channel to comprise an in-band 2.16GHz channel that overlaps the single transmission channel.

Example 53 is the at least one non-transitory computer-readable storagemedium of Example 51, the primary channel to comprise an out-of-band2.16 GHz channel that does not overlap the single transmission channel.

Example 54 is the at least one non-transitory computer-readable storagemedium of Example 46, the channel usage configuration to designatemultiple transmission channels.

Example 55 is the at least one non-transitory computer-readable storagemedium of Example 54, the channel usage configuration to designate two2.16 GHz transmission channels.

Example 56 is the at least one non-transitory computer-readable storagemedium of Example 55, the primary channel to comprise a same 2.16 GHzchannel as one of the two 2.16 GHz transmission channels.

Example 57 is the at least one non-transitory computer-readable storagemedium of Example 55, the primary channel to comprise a third 2.16 GHzchannel.

Example 58 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 57, the first field to comprise an indexvalue indicating the one or more transmission channels.

Example 59 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 57, the first field to comprise a bitmapindicating the one or more transmission channels.

Example 60 is the at least one non-transitory computer-readable storagemedium of Example 59, the bitmap to comprise 8 bits.

Example 61 is the at least one non-transitory computer-readable storagemedium of Example 60, each of the 8 bits to correspond to a respective2.16 GHz channel.

Example 62 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 61, the second field to comprise athree-bit value.

Example 63 is the at least one non-transitory computer-readable storagemedium of Example 62, the three-bit value to indicate which one of eight2.16 GHz channels constitutes the primary channel.

Example 64 is the at least one non-transitory computer-readable storagemedium of any of Examples 46 to 63, the PHY header to comprise a bitindicating whether channel aggregation is to be used for transmission ofthe packet.

Example 65 is the at least one non-transitory computer-readable storagemedium of Example 64, comprising instructions that, in response to beingexecuted at the wireless communication device, cause the wirelesscommunication device to set the bit to indicate that channel aggregationis to be used when the channel usage configuration designates more thanone transmission channel.

Example 66 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted at a wireless communication device, cause the wirelesscommunication device to decode a PHY header for a packet to be receivedfrom a remote device, the PHY header to indicate a channel usageconfiguration to be applied for reception of the packet, identify, basedon a first field comprised in the PHY header, a primary channeldesignated by the channel usage configuration, identify, based on asecond field comprised in the PHY header, one or more transmissionchannels designated by the channel usage configuration, and receive adata field of the packet via the one or more transmission channels.

Example 67 is the at least one non-transitory computer-readable storagemedium of Example 66, the channel usage configuration to designate asingle transmission channel.

Example 68 is the at least one non-transitory computer-readable storagemedium of Example 67, the single transmission channel to comprise a 2.16GHz channel.

Example 69 is the at least one non-transitory computer-readable storagemedium of Example 68, the primary channel to comprise a same 2.16 GHzchannel as the single transmission channel.

Example 70 is the at least one non-transitory computer-readable storagemedium of Example 68, the primary channel to comprise a second 2.16 GHzchannel.

Example 71 is the at least one non-transitory computer-readable storagemedium of Example 67, the single transmission channel to comprise a 4.32GHz channel, a 6.48 GHz channel, or an 8.64 GHz channel.

Example 72 is the at least one non-transitory computer-readable storagemedium of Example 71, the primary channel to comprise an in-band 2.16GHz channel that overlaps the single transmission channel.

Example 73 is the at least one non-transitory computer-readable storagemedium of Example 71, the primary channel to comprise an out-of-band2.16 GHz channel that does not overlap the single transmission channel.

Example 74 is the at least one non-transitory computer-readable storagemedium of Example 66, the channel usage configuration to designatemultiple transmission channels.

Example 75 is the at least one non-transitory computer-readable storagemedium of Example 74, the channel usage configuration to designate two2.16 GHz transmission channels.

Example 76 is the at least one non-transitory computer-readable storagemedium of Example 75, the primary channel to comprise a same 2.16 GHzchannel as one of the two 2.16 GHz transmission channels.

Example 77 is the at least one non-transitory computer-readable storagemedium of Example 75, the primary channel to comprise a third 2.16 GHzchannel.

Example 78 is the at least one non-transitory computer-readable storagemedium of any of Examples 66 to 77, the second field to comprise anindex value indicating the one or more transmission channels.

Example 79 is the at least one non-transitory computer-readable storagemedium of any of Examples 66 to 77, the second field to comprise abitmap indicating the one or more transmission channels.

Example 80 is the at least one non-transitory computer-readable storagemedium of Example 79, the bitmap to comprise 8 bits.

Example 81 is the at least one non-transitory computer-readable storagemedium of Example 80, each of the 8 bits to correspond to a respective2.16 GHz channel.

Example 82 is the at least one non-transitory computer-readable storagemedium of any of Examples 66 to 81, the first field to comprise athree-bit value.

Example 83 is the at least one non-transitory computer-readable storagemedium of Example 82, the three-bit value to indicate which one of eight2.16 GHz channels constitutes the primary channel.

Example 84 is the at least one non-transitory computer-readable storagemedium of any of Examples 66 to 83, the PHY header to comprise a bitindicating whether channel aggregation is to be used for transmission ofthe packet.

Example 85 is a method, comprising determining, by circuitry of awireless communication device, a channel usage configuration to beapplied for a transmission of a packet to a remote device, the channelusage configuration to designate a primary channel and one or moretransmission channels, generating a PHY header for the packet, the PHYheader to comprise a first field comprising information indicating theone or more transmission channels, and a second field comprisinginformation identifying the primary channel, and encoding the PHY headerfor wireless transmission.

Example 86 is the method of Example 85, the channel usage configurationto designate a single transmission channel.

Example 87 is the method of Example 86, the single transmission channelto comprise a 2.16 GHz channel.

Example 88 is the method of Example 87, the primary channel to comprisea same 2.16 GHz channel as the single transmission channel.

Example 89 is the method of Example 87, the primary channel to comprisea second 2.16 GHz channel.

Example 90 is the method of Example 86, the single transmission channelto comprise a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64 GHzchannel.

Example 91 is the method of Example 90, the primary channel to comprisean in-band 2.16 GHz channel that overlaps the single transmissionchannel.

Example 92 is the method of Example 90, the primary channel to comprisean out-of-band 2.16 GHz channel that does not overlap the singletransmission channel.

Example 93 is the method of Example 85, the channel usage configurationto designate multiple transmission channels.

Example 94 is the method of Example 93, the channel usage configurationto designate two 2.16 GHz transmission channels.

Example 95 is the method of Example 94, the primary channel to comprisea same 2.16 GHz channel as one of the two 2.16 GHz transmissionchannels.

Example 96 is the method of Example 94, the primary channel to comprisea third 2.16 GHz channel.

Example 97 is the method of any of Examples 85 to 96, the first field tocomprise an index value indicating the one or more transmissionchannels.

Example 98 is the method of any of Examples 85 to 96, the first field tocomprise a bitmap indicating the one or more transmission channels.

Example 99 is the method of Example 98, the bitmap to comprise 8 bits.

Example 100 is the method of Example 99, each of the 8 bits tocorrespond to a respective 2.16 GHz channel.

Example 101 is the method of any of Examples 85 to 100, the second fieldto comprise a three-bit value.

Example 102 is the method of Example 101, the three-bit value toindicate which one of eight 2.16 GHz channels constitutes the primarychannel.

Example 103 is the method of any of Examples 85 to 102, the PHY headerto comprise a bit indicating whether channel aggregation is to be usedfor transmission of the packet.

Example 104 is the method of Example 103, comprising setting the bit toindicate that channel aggregation is to be used when the channel usageconfiguration designates more than one transmission channel.

Example 105 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted on a computing device, cause the computing device to perform amethod according to any of Examples 85 to 104.

Example 106 is an apparatus, comprising means for performing a methodaccording to any of Examples 85 to 104.

Example 107 is a system, comprising the apparatus of Example 106, and atleast one radio frequency (RF) transceiver.

Example 108 is the system of Example 107, comprising at least oneprocessor.

Example 109 is the system of any of Examples 107 to 108, comprising atleast one RF antenna.

Example 110 is a method, comprising decoding, by circuitry of a wirelesscommunication device, a PHY header for a packet to be received from aremote device, the PHY header to indicate a channel usage configurationto be applied for reception of the packet, identifying, based on a firstfield comprised in the PHY header, a primary channel designated by thechannel usage configuration, identifying, based on a second fieldcomprised in the PHY header, one or more transmission channelsdesignated by the channel usage configuration, and receiving a datafield of the packet via the one or more transmission channels.

Example 111 is the method of Example 110, the channel usageconfiguration to designate a single transmission channel.

Example 112 is the method of Example 111, the single transmissionchannel to comprise a 2.16 GHz channel.

Example 113 is the method of Example 112, the primary channel tocomprise a same 2.16 GHz channel as the single transmission channel.

Example 114 is the method of Example 112, the primary channel tocomprise a second 2.16 GHz channel.

Example 115 is the method of Example 111, the single transmissionchannel to comprise a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64GHz channel.

Example 116 is the method of Example 115, the primary channel tocomprise an in-band 2.16 GHz channel that overlaps the singletransmission channel.

Example 117 is the method of Example 115, the primary channel tocomprise an out-of-band 2.16 GHz channel that does not overlap thesingle transmission channel.

Example 118 is the method of Example 110, the channel usageconfiguration to designate multiple transmission channels.

Example 119 is the method of Example 118, the channel usageconfiguration to designate two 2.16 GHz transmission channels.

Example 120 is the method of Example 119, the primary channel tocomprise a same 2.16 GHz channel as one of the two 2.16 GHz transmissionchannels.

Example 121 is the method of Example 119, the primary channel tocomprise a third 2.16 GHz channel.

Example 122 is the method of any of Examples 110 to 121, the secondfield to comprise an index value indicating the one or more transmissionchannels.

Example 123 is the method of any of Examples 110 to 121, the secondfield to comprise a bitmap indicating the one or more transmissionchannels.

Example 124 is the method of Example 123, the bitmap to comprise 8 bits.

Example 125 is the method of Example 124, each of the 8 bits tocorrespond to a respective 2.16 GHz channel.

Example 126 is the method of any of Examples 110 to 125, the first fieldto comprise a three-bit value.

Example 127 is the method of Example 126, the three-bit value toindicate which one of eight 2.16 GHz channels constitutes the primarychannel.

Example 128 is the method of any of Examples 110 to 127, the PHY headerto comprise a bit indicating whether channel aggregation is to be usedfor transmission of the packet.

Example 129 is at least one non-transitory computer-readable storagemedium comprising a set of instructions that, in response to beingexecuted on a computing device, cause the computing device to perform amethod according to any of Examples 110 to 128.

Example 130 is an apparatus, comprising means for performing a methodaccording to any of Examples 110 to 128.

Example 131 is a system, comprising the apparatus of Example 130, and atleast one radio frequency (RF) transceiver.

Example 132 is the system of Example 131, comprising at least oneprocessor.

Example 133 is the system of any of Examples 131 to 132, comprising atleast one RF antenna.

Example 134 is an apparatus, comprising means for determining a channelusage configuration to be applied for a transmission of a packet from awireless communication device to a remote device, the channel usageconfiguration to designate a primary channel and one or moretransmission channels, means for generating a PHY header for the packet,the PHY header to comprise a first field comprising informationindicating the one or more transmission channels, and a second fieldcomprising information identifying the primary channel, and means forencoding the PHY header for wireless transmission.

Example 135 is the apparatus of Example 134, the channel usageconfiguration to designate a single transmission channel.

Example 136 is the apparatus of Example 135, the single transmissionchannel to comprise a 2.16 GHz channel.

Example 137 is the apparatus of Example 136, the primary channel tocomprise a same 2.16 GHz channel as the single transmission channel.

Example 138 is the apparatus of Example 136, the primary channel tocomprise a second 2.16 GHz channel.

Example 139 is the apparatus of Example 135, the single transmissionchannel to comprise a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64GHz channel.

Example 140 is the apparatus of Example 139, the primary channel tocomprise an in-band 2.16 GHz channel that overlaps the singletransmission channel.

Example 141 is the apparatus of Example 139, the primary channel tocomprise an out-of-band 2.16 GHz channel that does not overlap thesingle transmission channel.

Example 142 is the apparatus of Example 134, the channel usageconfiguration to designate multiple transmission channels.

Example 143 is the apparatus of Example 142, the channel usageconfiguration to designate two 2.16 GHz transmission channels.

Example 144 is the apparatus of Example 143, the primary channel tocomprise a same 2.16 GHz channel as one of the two 2.16 GHz transmissionchannels.

Example 145 is the apparatus of Example 143, the primary channel tocomprise a third 2.16 GHz channel.

Example 146 is the apparatus of any of Examples 134 to 145, the firstfield to comprise an index value indicating the one or more transmissionchannels.

Example 147 is the apparatus of any of Examples 134 to 145, the firstfield to comprise a bitmap indicating the one or more transmissionchannels.

Example 148 is the apparatus of Example 147, the bitmap to comprise 8bits.

Example 149 is the apparatus of Example 148, each of the 8 bits tocorrespond to a respective 2.16 GHz channel.

Example 150 is the apparatus of any of Examples 134 to 149, the secondfield to comprise a three-bit value.

Example 151 is the apparatus of Example 150, the three-bit value toindicate which one of eight 2.16 GHz channels constitutes the primarychannel.

Example 152 is the apparatus of any of Examples 134 to 151, the PHYheader to comprise a bit indicating whether channel aggregation is to beused for transmission of the packet.

Example 153 is the apparatus of Example 152, comprising means forsetting the bit to indicate that channel aggregation is to be used whenthe channel usage configuration designates more than one transmissionchannel.

Example 154 is a system, comprising an apparatus according to any ofExamples 134 to 153, and at least one radio frequency (RF) transceiver.

Example 155 is the system of Example 154, comprising at least oneprocessor.

Example 156 is the system of any of Examples 154 to 155, comprising atleast one RF antenna.

Example 157 is an apparatus, comprising means for decoding, at awireless communication device, a PHY header for a packet to be receivedfrom a remote device, the PHY header to indicate a channel usageconfiguration to be applied for reception of the packet, means foridentifying, based on a first field comprised in the PHY header, aprimary channel designated by the channel usage configuration, means foridentifying, based on a second field comprised in the PHY header, one ormore transmission channels designated by the channel usageconfiguration, and means for receiving a data field of the packet viathe one or more transmission channels.

Example 158 is the apparatus of Example 157, the channel usageconfiguration to designate a single transmission channel.

Example 159 is the apparatus of Example 158, the single transmissionchannel to comprise a 2.16 GHz channel.

Example 160 is the apparatus of Example 159, the primary channel tocomprise a same 2.16 GHz channel as the single transmission channel.

Example 161 is the apparatus of Example 159, the primary channel tocomprise a second 2.16 GHz channel.

Example 162 is the apparatus of Example 158, the single transmissionchannel to comprise a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64GHz channel.

Example 163 is the apparatus of Example 162, the primary channel tocomprise an in-band 2.16 GHz channel that overlaps the singletransmission channel.

Example 164 is the apparatus of Example 162, the primary channel tocomprise an out-of-band 2.16 GHz channel that does not overlap thesingle transmission channel.

Example 165 is the apparatus of Example 157, the channel usageconfiguration to designate multiple transmission channels.

Example 166 is the apparatus of Example 165, the channel usageconfiguration to designate two 2.16 GHz transmission channels.

Example 167 is the apparatus of Example 166, the primary channel tocomprise a same 2.16 GHz channel as one of the two 2.16 GHz transmissionchannels.

Example 168 is the apparatus of Example 166, the primary channel tocomprise a third 2.16 GHz channel.

Example 169 is the apparatus of any of Examples 157 to 168, the secondfield to comprise an index value indicating the one or more transmissionchannels.

Example 170 is the apparatus of any of Examples 157 to 168, the secondfield to comprise a bitmap indicating the one or more transmissionchannels.

Example 171 is the apparatus of Example 170, the bitmap to comprise 8bits.

Example 172 is the apparatus of Example 171, each of the 8 bits tocorrespond to a respective 2.16 GHz channel.

Example 173 is the apparatus of any of Examples 157 to 172, the firstfield to comprise a three-bit value.

Example 174 is the apparatus of Example 173, the three-bit value toindicate which one of eight 2.16 GHz channels constitutes the primarychannel.

Example 175 is the apparatus of any of Examples 157 to 174, the PHYheader to comprise a bit indicating whether channel aggregation is to beused for transmission of the packet.

Example 176 is a system, comprising an apparatus according to any ofExamples 157 to 175, and at least one radio frequency (RF) transceiver.

Example 177 is the system of Example 176, comprising at least oneprocessor.

Example 178 is the system of any of Examples 176 to 177, comprising atleast one RF antenna.

Numerous specific details have been set forth herein to provide athorough understanding of the embodiments. It will be understood bythose skilled in the art, however, that the embodiments may be practicedwithout these specific details. In other instances, well-knownoperations, components, and circuits have not been described in detailso as not to obscure the embodiments. It can be appreciated that thespecific structural and functional details disclosed herein may berepresentative and do not necessarily limit the scope of theembodiments.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are not intendedas synonyms for each other. For example, some embodiments may bedescribed using the terms “connected” and/or “coupled” to indicate thattwo or more elements are in direct physical or electrical contact witheach other. The term “coupled,” however, may also mean that two or moreelements are not in direct contact with each other, but yet stillco-operate or interact with each other.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

It should be noted that the methods described herein do not have to beexecuted in the order described, or in any particular order. Moreover,various activities described with respect to the methods identifiedherein can be executed in serial or parallel fashion.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. It is to be understood that the abovedescription has been made in an illustrative fashion, and not arestrictive one. Combinations of the above embodiments, and otherembodiments not specifically described herein will be apparent to thoseof skill in the art upon reviewing the above description. Thus, thescope of various embodiments includes any other applications in whichthe above compositions, structures, and methods are used.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. § 1.72(b), requiring an abstract that will allowthe reader to quickly ascertain the nature of the technical disclosure.It is submitted with the understanding that it will not be used tointerpret or limit the scope or meaning of the claims. In addition, inthe foregoing Detailed Description, it can be seen that various featuresare grouped together in a single embodiment for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting an intention that the claimed embodimentsrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter lies in lessthan all features of a single disclosed embodiment. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate preferred embodiment. In theappended claims, the terms “including” and “in which” are used as theplain-English equivalents of the respective terms “comprising” and“wherein,” respectively. Moreover, the terms “first,” “second,” and“third,” etc. are used merely as labels, and are not intended to imposenumerical requirements on their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. An apparatus, comprising: a memory; and aprocessing circuit coupled to the memory, the logic to: generate a PHYheader for the packet, the PHY header to comprise: a first fieldcomprising information indicating the one or more data transmissionchannels, the first field to comprise a bitmap, the bitmap to comprise 8bits, each bit of the 8 bits to correspond to a respective 2.16gigahertz (GHz) channel; and a second field comprising informationidentifying the primary channel, the second field to comprise athree-bit value to indicate the primary channel, wherein the three-bitvalue comprises an index value, the index value based on primarychannel; and encode the PHY header for wireless transmission.
 2. Theapparatus of claim 1, the second field to comprise a three-bit valueindicating which one of the 2.16 GHz channels constitutes the primarychannel.
 3. The apparatus of claim 1, the PHY header to comprise asecond field to comprise a three-bit value to indicate the primarychannel.
 4. The apparatus of claim 1, the bitmap to describe a 2.16 GHzchannel, a 4.32 GHz channel, a 6.48 GHz channel, or an 8.64 GHz channel.5. The apparatus of claim 1, the bitmap to describe a 2.16 GHz+2.16 GHzchannel.
 6. The apparatus of claim 1, the processing circuit coupledwith a radio interface, the radio interface comprising a transmitter anda receiver.
 7. The apparatus of claim 6, the radio interface coupledwith at least one antenna.
 8. An apparatus, comprising: a memory; and aprocessing circuit coupled to the memory, the logic to: decode a PHYheader for the packet, the PHY header to comprise: a first field tocomprise a bitmap, the bitmap to comprise 8 bits, each bit of the 8 bitsto correspond to a respective 2.16 gigahertz (GHz) channel; and a bitindicating whether aggregation of more than one channel is to be usedfor transmission of the packet or aggregation of more than one channelis not to be used.
 9. The apparatus of claim 8, the second field tocomprise a three-bit value indicating which one of the 2.16 GHz channelsconstitutes the primary channel.
 10. The apparatus of claim 8, the PHYheader to comprise a second field to comprise a three-bit value toindicate the primary channel.
 11. The apparatus of claim 8, the bitmapto describe a 2.16 GHz channel, a 4.32 GHz channel, a 6.48 GHz channel,or an 8.64 GHz channel.
 12. The apparatus of claim 8, the bitmap todescribe a 2.16 GHz+2.16 GHz channel.
 13. The apparatus of claim 8, theprocessing circuit coupled with a radio interface, the radio interfacecomprising a transmitter and a receiver.
 14. The apparatus of claim 13,the radio interface coupled with at least one antenna.
 15. At least onenon-transitory computer-readable storage medium comprising a set ofinstructions that, in response to being executed at a wirelesscommunication device, cause the wireless communication device to:generate a PHY header for the packet, the PHY header to comprise: afirst field to comprise a bitmap, the bitmap to comprise 8 bits, eachbit of the 8 bits to correspond to a respective 2.16 gigahertz (GHz)channel; and a bit indicating whether aggregation of more than onechannel is to be used for transmission of the packet or aggregation ofmore than one channel is not to be used; and encode the PHY header forwireless transmission.
 16. The at least one non-transitorycomputer-readable storage medium of claim 15, the second field tocomprise a three-bit value indicating which one of the 2.16 GHz channelsconstitutes the primary channel.
 17. The at least one non-transitorycomputer-readable storage medium of claim 15, the PHY header to comprisea second field to comprise a three-bit value to indicate the primarychannel.
 18. The at least one non-transitory computer-readable storagemedium of claim 15, the bitmap to describe a 2.16 GHz channel, a 4.32GHz channel, a 6.48 GHz channel, or an 8.64 GHz channel.
 19. The atleast one non-transitory computer-readable storage medium of claim 15,the bitmap to describe a 2.16 GHz+2.16 GHz channel.
 20. At least onenon-transitory computer-readable storage medium comprising a set ofinstructions that, in response to being executed at a wirelesscommunication device, cause the wireless communication device to: decodea PHY header for the packet, the PHY header to comprise: a first fieldto comprise a bitmap, the bitmap to comprise 8 bits, each bit of the 8bits to correspond to a respective 2.16 gigahertz (GHz) channel; and abit indicating whether aggregation of more than one channel is to beused for transmission of the packet or aggregation of more than onechannel is not to be used.
 21. The at least one non-transitorycomputer-readable storage medium of claim 20, the second field tocomprise a three-bit value indicating which one of the 2.16 GHz channelsconstitutes the primary channel.
 22. The at least one non-transitorycomputer-readable storage medium of claim 20, the PHY header to comprisea second field to comprise a three-bit value to indicate the primarychannel.
 23. The at least one non-transitory computer-readable storagemedium of claim 20, the bitmap to describe a 2.16 GHz channel, a 4.32GHz channel, a 6.48 GHz channel, or an 8.64 GHz channel.
 24. The atleast one non-transitory computer-readable storage medium of claim 20,the bitmap to describe a 2.16 GHz+2.16 GHz channel.